Pucch resource allocation with enhanced pdcch

ABSTRACT

Embodiments of the present disclosure include methods, apparatuses, and instructions for receiving at a user equipment (UE) of a third generation partnership project (3GPP) network an offset value selected from a plurality of offset values in downlink control information. The UE also receives one or more enhanced control channel elements (eCCEs) of an enhanced physical downlink control channel (ePDCCH). The UE may then determine an allocation of an uplink resource for a transmission on a physical uplink control channel (PUCCH) based at least in part on the index of a first eCCE and the offset value.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. patent application Ser.No. 13/673,791, filed Nov. 9, 2012, entitled “PUCCH RESOURCE ALLOCATIONWITH ENHANCED PDCCH,” which claims priority to U.S. Provisional PatentApplications No. 61/653,369, filed May 30, 2012, entitled “AdvancedWireless Communication Systems and Techniques,” and No. 61/707,784,filed Sep. 28, 2012, entitled “Advanced Wireless Communication Systemsand Techniques,” the entire disclosures of which are hereby incorporatedby reference in their entirety.

FIELD

Embodiments of the present invention relate generally to the technicalfield of resource allocation in third generation partnership project(3GPP) networks. Specifically, embodiments describe uplink resourceallocation when a 3GPP network is sending downlink signals on both aphysical downlink control channel (PDCCH) and an enhanced physicaldownlink control channel (ePDCCH).

BACKGROUND

The background description provided herein is for the purpose ofgenerally presenting the context of the disclosure. Work of thepresently named inventors, to the extent it is described in thisbackground section, as well as aspects of the description that may nototherwise qualify as prior art at the time of filing, are neitherexpressly nor impliedly admitted as prior art against the presentdisclosure. Unless otherwise indicated herein, the approaches describedin this section are not prior art to the claims in the presentdisclosure and are not admitted to be prior art by inclusion in thissection.

In 3GPP network, the physical uplink control channel (PUCCH) is used totransmit uplink control information (UCI) from a UE to a 3GPP eNodebB(eNB). An example of the UCI information is an acknowledgement signal ina hybrid-ARQ (HARM) process. Typically, PUCCH resources are dynamicallyallocated to a mobile station based upon the lowest carrier controlelement (CCE) index of a signal transmitted on the PDCCH by the eNBusing one or more CCEs. Because the PDCCH transmission is unique to agiven UE, use of the CCE index would result in the UE being assigned aunique uplink resource on the PUCCH.

However, an ePDCCH using one or more enhanced carrier control elements(eCCEs) has recently been introduced to the 3GPP specifications. Theuplink resource of the PUCCH may be based on the lowest eCCE index forone or more eCCEs used for a transmission on the ePDCCH. In certaininstances the lowest CCE index and the lowest eCCE index may be thesame. In these instances, an uplink resource allocated to a first UEusing the lowest CCE index of the PDCCH may be the same as an uplinkresource allocated to a second UE using the lowest eCCE index of theePDCCH, resulting in a resource allocation collision.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings. To facilitatethis description, like reference numerals designate like structuralelements. Embodiments are illustrated by way of example and not by wayof limitation in the figures of the accompanying drawings.

FIG. 1 schematically illustrates a high-level example of a networksystem comprising a UE and an eNB, in accordance with variousembodiments.

FIG. 2 illustrates an exemplary uplink resource index, in accordancewith various embodiments.

FIG. 3 illustrates exemplary uplink resource offset values, inaccordance with various embodiments.

FIG. 4 illustrates other exemplary uplink resource offset values, inaccordance with various embodiments.

FIG. 5 illustrates other exemplary uplink resource offset values, inaccordance with various embodiments.

FIG. 6 schematically illustrates an example system that may be used topractice various embodiments described herein.

DETAILED DESCRIPTION

Apparatuses, methods, and storage media are described herein forallocating uplink resources. In certain embodiments, uplink resourcesrelated to a CCE and information received in a transmission on the PDCCHmay be allocated according to a first set of values. Uplink resourcesrelated to an eCCE and information received in a transmission on theePDCCH may be allocated according to a similar set of values with theaddition of an offset value. In certain embodiments, for example whenUEs are using transmit diversity for PUCCH, it may be desirable for theoffset values to be even. In some embodiments, the offset values may benegative. In some embodiments, the offset values may be specificallysignaled by the RRC or dictated by the antenna ports that are associatedwith the ePDCCH transmission. In certain embodiments, the resourceallocation may be based at least in part on a starting offset value.

In the following detailed description, reference is made to theaccompanying drawings which form a part hereof wherein like numeralsdesignate like parts throughout, and in which is shown by way ofillustration embodiments that may be practiced. It is to be understoodthat other embodiments may be utilized and structural or logical changesmay be made without departing from the scope of the present disclosure.Therefore, the following detailed description is not to be taken in alimiting sense, and the scope of embodiments is defined by the appendedclaims and their equivalents.

Various operations may be described as multiple discrete actions oroperations in turn, in a manner that is most helpful in understandingthe claimed subject matter. However, the order of description should notbe construed as to imply that these operations are necessarily orderdependent. In particular, these operations may not be performed in theorder of presentation. Operations described may be performed in adifferent order than the described embodiment. Various additionaloperations may be performed and/or described operations may be omittedin additional embodiments.

For the purposes of the present disclosure, the phrases “A and/or B” and“A or B” mean (A), (B), or (A and B). For the purposes of the presentdisclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B),(A and C), (B and C), or (A, B and C).

The description may use the phrases “in an embodiment,” or “inembodiments,” which may each refer to one or more of the same ordifferent embodiments. Furthermore, the terms “comprising,” “including,”“having,” and the like, as used with respect to embodiments of thepresent disclosure, are synonymous.

FIG. 1 schematically illustrates a wireless communication network 100 inaccordance with various embodiments. Wireless communication network 100(hereinafter “network 100”) may be an access network of a 3GPP LTEnetwork such as evolved universal terrestrial radio access network(E-UTRAN). The network 100 may include an eNB 105, configured towirelessly communicate with a UE 110.

As shown in FIG. 1, the UE 110 may include a transceiver module 120. Thetransceiver module 120 may be further coupled with one or more of aplurality of antennas 125 of the UE 110 for communicating wirelesslywith other components of the network 100, e.g., eNB 105. The antennas125 may be powered by a power amplifier 130 which may be a component ofthe transceiver module 120, as shown in FIG. 1, or may be a separatecomponent of the UE 110. In one embodiment, the power amplifier 130provides the power for all transmissions on the antennas 125. In otherembodiments, there may be multiple power amplifiers on the UE 110. Theuse of multiple antennas 125 may allow for the UE 110 to use transmitdiversity techniques such as spatial orthogonal resource transmitdiversity (SORTD). In certain embodiments the transceiver module 120 maycontain both transmission and reception circuitry. In other embodiments,the transceiver module 120 may be replaced by transmitting circuitry andreceiving circuitry which are separate from one another (not shown). Inother embodiments, the transceiver module 120 may be coupled withprocessing circuitry configured to alter, process, or transform signalsor data received from, or sent to, the transceiver module 120 (notshown).

FIG. 2 depicts exemplary CCE/eCCE indices 200. The exemplary indicesinclude a lowest index #m and sequentially increasing indices #m+1, #m+2. . . #m+7. As described above, the lowest CCE index of a PDCCHtransmission may, in some instances, be the same as the lowest eCCEindex of an ePDCCH transmission. For example, the lowest CCE index andthe lowest eCCE index may be the same, for example both using index#m+2. If the PUCCH transmissions of a first UE and the PUCCHtransmissions of a second UE were scheduled using the CCE/eCCE index#m+2, the transmissions of PUCCHs may conflict due to using the sameCCE/eCCE indices.

However, a conflicting transmission may be avoided if an offset value isused for dynamic resource allocation of uplink resources using an eCCE.In some embodiments the offset values may be configured by a radioresource control (RRC) entity of the network 100, however other entitiesmay configure the offset values in other embodiments. In someembodiments the offset value may be an A/N Resource Indicator (ARI). Inother embodiments the offset value may be related to the antenna portused by the eNB 105 to transmit data to the UE 110 on the ePDCCH.

As an example using the offset value, if a UE in a frequency divisionduplex (FDD) scenario is using transmit diversity for PUCCH such asSORTD, then the PUCCH resources of the UE may be allocated using the CCEindex according to: n_(PUCCH) ^((1,{tilde over (p)}) ⁰⁾=n_(CCE)+N_(PUCCH) ⁽¹⁾ and n_(PUCCH) ^((1,{tilde over (p)}) ¹⁾=n_(CCE)+1+N_(PUCCH) ⁽¹⁾ for antenna ports 0 and 1, respectively, wheren_(PUCCH) ^((1,{tilde over (p)}) ⁰ ⁾is the PUCCH resource for port 0,n_(PUCCH) ^((1,{tilde over (p)}) ¹ ⁾ is the PUCCH resource for port 1,n_(CCE) is the CCE index and N_(PUCCH) ⁽¹⁾ is a pre-configured value. InFDD carrier aggregation using PUCCH format 1b with channel selection, aPUCCH resource may be allocated according to n_(PUCCH,j)⁽¹⁾=n_(CCE)+N_(PUCCH) ⁽¹⁾ and another PUCCH resource may be allocatedaccording to n_(PUCCH,j+1) ⁽¹⁾=n_(CCE)+1+N_(PUCCH) ⁽¹⁾.

For a time division duplex (TDD) scenario, the resources for antennaports 0 and 1 may be determined by n_(PUCCH) ^((1,{tilde over (p)}) ⁰⁾=value+n_(CCE)+N_(PUCCH) ⁽¹⁾ and n_(PUCCH) ^((1,{tilde over (p)}) ¹⁾=value+n_(CCE)+1+N_(PUCCH) ⁽¹⁾, respectively where value is a valueassociated with one or more of the specific subframes, a signaled value,a physical downlink shared channel, or a semi-persistent scheduling(SPS) value as described, for example, in 3GPP technical specification36.213 v 10.5.0 (2012-03).

By contrast, the PUCCH resources of the UE in the FDD scenario may beallocated using the eCCE according to n_(PUCCH) ^((1,{tilde over (p)}) ⁰⁾=n_(eCCE)+N_(PUCCH) ^((1,k))+n_(offset) and n_(PUCCH)^((1,{tilde over (p)}) ¹ ⁾=n_(eCCE)+1+N_(PUCCH) ^((1,k))+n_(offset) forantenna ports 0 and 1, respectively where N_(PUCCH) ^((1,k)) representsthe UE specific starting offset for PUCCH resource for ePDCCH set k. Incertain embodiments, there may be 2 ePDCCH sets, so k may be equal to 0or 1, although in other embodiments there may be more or less ePDCCHsets or k may have some other value for a given ePDCCH set. Further, thePUCCH resources of the UE in the TDD scenario may be allocated using theeCCE according to n_(PUCCH) ^((1,{tilde over (p)}) ⁰⁾=value+n_(eCCE)+N_(PUCCH) ^((1,k))+n_(offset), for antenna port 0 andn_(PUCCH) ^((1,{tilde over (p)}) ¹ ⁾=value+n_(eCCE)+1+N_(PUCCH)^((1,k))+n_(offset), for antenna port 1.

In some embodiments, n_(offset), may be an offset value that istransmitted to the UE via downlink control information (DCI) transmittedon the PDCCH or ePDCCH. As noted above, in some embodiments n_(offset)may be an ARI. Alternatively, the offset value n_(offset) may be anantenna specific offset k_(p) associated with antenna port p, where p isthe antenna port allocated to the first CCE of the corresponding ePDCCH.In embodiments utilizing distributed ePDCCH, k_(p) may be equal to zerowhen p is equal to 107 or 109. In embodiments utilizing localizedePDCCH, k_(p) may be equal to p−107 when p is equal to 107, 108, 109, or110. In these embodiments, n_(offset) may equal 2·m·k_(p) where m is aninteger. In certain embodiments, m may be equal to 1 and thereforen_(offset)=2·k_(p).

In other embodiments, when using the antenna specific offset k_(p),n_(offset) may be equal to k_(p)), and the FDD resource allocation maythen become n_(PUCCH) ^((1,{tilde over (p)}) ⁰ ⁾=n_(eCCE)+N_(PUCCH)^((1,k))+k_(p) and n_(PUCCH) ^((1,{tilde over (p)}) ¹⁾n_(eCCE)+1+N_(PUCCH)+k_(p) for antenna ports 0 and 1, respectivelywhere N_(PUCCH) ^((1,k)) represents the UE specific starting offset forPUCCH resource for ePDCCH set k, as described above. The TDD resourceallocation may likewise become n_(PUCCH) ^((1,{tilde over (p)}) ⁰⁾=value+n_(eCCE)+N_(PUCCH) ^((1,k))+k_(p), and n_(PUCCH)^((1,{tilde over (p)}) ¹ ⁾=value+n_(eCCE)+1+N_(PUCCH) ^((1,k))+k_(p),for antenna ports 0 and 1, respectively.

In certain embodiments, a combination of the n_(offset) values, forexample a DCI signaled n_(offset) value associated with ARI and ann_(offset) value associated with an antenna specific offset value suchas k_(p) may be used. For ease of understanding the following example,the n_(offset) associated with a DCI-signaled value such as an ARI willbe referred to as n_(ARI). The n_(offset) associated with the antennaport will be referred to as n_(antenna). It will be understood thatn_(antenna) may be equal to values such a k_(p) or a multiplied value ofk_(p) such as 2k_(p) or 2mk_(p) as described above.

As an example, for localized ePDCCH transmission, the uplink resourcesin the FDD scenario may be allocated according to n_(PUCCH)^((1,{tilde over (p)}) ⁰ ⁾=n_(eCCE)+N_(PUCCH)^((1,k))+n_(ARI)+n_(antenna) and n_(PUCCH) ^((1,{tilde over (p)}) ¹⁾=n_(eCCE)+1+N_(PUCCH) ^((1,k))+n_(ARI)+n_(antenna), for antenna ports 0and 1, respectively. For distributed ePDCCH transmission, the uplinkresources in the FDD scenario may be allocated according to n_(PUCCH)^((1,{tilde over (p)}) ⁰ ⁾=n_(eCCE)+N_(PUCCH) ^((1,k))+n_(offset) andn_(PUCCH) ^((1,{tilde over (p)}) ¹ ⁾=n_(eCCE)+1+N_(PUCCH)^((1,k))+n_(offset), for antenna ports 0 and 1, respectively.

For localized ePDCCH transmission, the uplink resources in the TDDscenario may be allocated according to n_(PUCCH) ^((1,{tilde over (p)})⁰ ⁾=value+n_(eCCE)+N_(PUCCH) ^((1,k))+n_(ARI)+n_(antenna) and n_(PUCCH)^((1,{tilde over (p)}) ¹ ⁾=value+n_(eCCE)+1+N_(PUCCH)^((1,k))+n_(ARI)+n_(antenna), for antenna ports 0 and 1, respectively.For distributed ePDCCH transmission, the uplink resources in the TDDscenario may be allocated according to n_(PUCCH) ^((1,{tilde over (p)})⁰ ⁾=value+n_(eCCE)+N_(PUCCH) ^((1,k))+n_(offset) and n_(PUCCH)^((1,{tilde over (p)}) ¹ ⁾=value+n_(eCCE)+1+N_(PUCCH)^((1,k))+n_(offset), for antenna ports 0 and 1, respectively.

In certain embodiments, the RRC configuration N_(PUCCH,ePDCCH) ⁽¹⁾ toindicate the starting offset for dynamic resource allocation may beintroduced. In this embodiment, N_(PUCCH,ePDCCH) ⁽¹⁾ may replaceN_(PUCCH) ⁽¹⁾ in the above equations for the FDD and TDD resourceallocation.

FIG. 3 depicts exemplary n_(offset) values 300 that may be signaled invarious embodiments. As discussed above, the n_(offset) values may besignaled via the DCI of the ePDCCH. In some embodiments, the discussedn_(offset) values may be the ARI values discussed above. The exemplaryn_(offset) values 300 correspond to a set of values 305 signaled on theDCI.

In FIG. 3, a first set of n_(offset) values 310 may correspond to theset of values 305 signaled on the DCI in a first embodiment. Forexample, an n_(offset) of 0, 2, 4, or 6 may correspond to a DCI signalof 00, 01, 10, or 11, respectively. A second set of n_(offset) values315 may correspond to the set of values 305 signaled on the DCI in asecond embodiment. For example, an n_(offset) of −2, 0, 2, or 4 maycorrespond to a DCI signal of 00, 01, 10, or 11, respectively. A thirdset of n_(offset) values 320 may correspond to the set of values 305signaled on the DCI in a third embodiment. For example, an n_(offset) of−4, −2, 0, or 2 may correspond to a DCI signal of 00, 01, 10, or 11,respectively. A fourth set of n_(offset) values 325 may correspond tothe set of values 305 signaled on the DCI in a fourth embodiment. Forexample, an n_(offset) of −6, −4, −2, or 0 may correspond to a DCIsignal of 00, 01, 10, or 11, respectively. A fifth set of n_(offset)values 330 may correspond to the set of values 305 signaled on the DCIin a fifth embodiment. For example, an n_(offset) of 0, 2, 6, or 8 maycorrespond to a DCI signal of 00, 01, 10, or 11, respectively.

It may be desirable for the n_(offset) to be an even value so that aresource scheduler can consider two different resources for two antennaports when using a transmit diversity configuration such as SORTD or forFDD carrier aggregation using PUCCH format 1b with channel selection tomaximize the likelihood of collision avoidance. As shown above, uplinkresource allocation between ports 0 and 1, or uplink resource allocationfor PUCCH format 1b with channel selection, may be incremented by avalue of 1. In other words, if port 0 uses an uplink resourcecorresponding to #m+2, then port 1 may use an uplink resourcecorresponding to #m+3. In this example, the uplink resource allocationcorresponding to the eCCE may need to be incremented by an even value sothat the uplink resource allocation of port 0 based on the eCCE does notcollide with the uplink resource allocation of port 1 based on the CCE.For example, referring to FIG. 2, if the lowest CCE index is #m+2, andthe lowest eCCE index is #m+4, then an n_(offset) value of −1 mayproduce a collision because both the uplink resource allocation producedusing the CCE for port 1 and the uplink resource allocation producedusing the eCCE for port 0 may point to the uplink resource correspondingto #m+3. Alternatively, if the lowest CCE index is #m+2 and the lowesteCCE index is #m+2, then an n_(offset) value of 1 may produce acollision because both the uplink resource allocation produced using theCCE for port 1 and the uplink resource allocation produced using theeCCE for port 0 may point to the uplink resource corresponding to #m+3.

As will be recognized, it may be desirable in certain embodiments for atleast one of the possible n_(offset) values to be 0 to allow for aneutralization of the n_(offset) value if future standards revisionsrender the n_(offset) value undesirable or obsolete. However, othern_(offset) value sets may not include an n_(offset) value of 0. In someembodiments, it may be desirable for at least one n_(offset) value to benegative to account for a large aggregation level for previous PDCCHs,i.e. the number of consecutive CCEs used to transmit the previousPDCCHs, although other embodiments may have all positive (or allnegative) n_(offset) values. Finally, the n_(offset) values shown insets 310, 315, 320, 325, and 330 are merely exemplary and greater orlesser values may be desirable.

Using more or less bits to indicate the n_(offset) value may bedesirable to allow greater or lesser degrees of freedom in signaling ann_(offset) value. For example, using 2 bits allows 4 degrees of freedom,however using 3 bits may allow 8 degrees of freedom, and using x bitsmay allow 2^(x) degrees of freedom. In some embodiments it may bedesirable for the purposes of power savings or signal overhead to useonly a single bit to signal the n_(offset) value. In general the DCIbits for the offset can be defined by adding bits to an existing DCIfield, or by reusing an existing field in the DCI.

For example, FIG. 4 depicts exemplary n_(offset) values 400 forembodiments where only a single bit is used in the set of values 405signaled on the DCI. Similarly to FIG. 3, the discussed n_(offset)values may be the ARI values discussed above. For example, a sixth setof n_(offset) values 410 may correspond to the set of values 405signaled on the DCI in a sixth embodiment. For example, an n_(offset) of−2 or 0 may correspond to a DCI signal of 0 or 1, respectively. Aseventh set of n_(offset) values 415 may correspond to the set of values405 signaled on the DCI in a seventh embodiment. For example, ann_(offset) of 0 or 2 may correspond to a DCI signal of 0 or 1,respectively.

In some embodiments, the offset values may contain a combination of evenand odd values. FIG. 5 depicts exemplary n_(offset) values 500 forembodiments containing a combination of even and odd values. Similarlyto FIGS. 3 and 4, the discussed n_(offset) values may be the ARI valuesdiscussed above. In FIG. 5, an eighth set of n_(offset) values 510 maycorrespond to the set of values 505 signaled on the DCI in an eighthembodiment. For example, an n_(offset) of −4, −2, 0, or 1 may correspondto a DCI signal of 00, 01, 10, or 11, respectively. A ninth set ofn_(offset) values 515 may correspond to the set of values 505 signaledon the DCI in a ninth embodiment. For example, an n_(offset) of −2, 0,1, or 2 may correspond to a DCI signal of 00, 01, 10, or 11,respectively. A tenth set of n_(offset) values 520 may correspond to theset of values 505 signaled on the DCI in a tenth embodiment. Forexample, an n_(offset) of −2, −1, 0, or 2 may correspond to a DCI signalof 00, 01, 10, or 11, respectively.

The use of a combination of odd values and even values may be desirablefor several reasons. First, a scaling value may be applied to maximizethe flexibility of the n_(offset) values. For example, if transmitdiversity such as SORTD is not used in the PUCCH transmission, then anon-even n_(offset) value may be acceptable. However, if the PUCCH islater transmitted using SORTD, then an even n_(offset) value may bedesirable. A combination of odd and even values may allow for bothscenarios, because a scaling factor such as 2 may be applied so that theodd values become the even values desired for the SORTD transmission. Asan example and referring to the n_(offset) values 515 of the ninthembodiment, the use of a scaling factor such as 2 may make the values(−2, 0, 1, 2) become the even values (−4, 0, 2, 4). In some embodimentsthe RRC may configure the scaling factor, while in other embodiments theeNB may configure the scaling factor for use by the UE for the PUCCHtransmission.

In certain embodiments where the ePDCCH is used in a stand-alone newcarrier type (NCT), for example as a PCell, the above describedembodiments may be altered. For example, the n_(offset) value may bemaintained considering possible future extensions such as downlinkmultiuser multiple-input and multiple output (MU-MIMO) or coordinatedmultipoint transmission (CoMP). Alternatively, the n_(offset) value maybe effectively removed, for example by always setting the n_(offset)value to 0. In this instance the n_(offset) value may be used as avirtual cyclic redundancy check (CRC) field. In other embodiments, then_(offset) value may be completely removed from the DCI.

As discussed above, in certain embodiments starting offsets for dynamicresource allocation may be provided by RRC parameters indicated by RRCsignaling. In those embodiments, at least one n_(offset) value maycontain at least one of the RRC parameters. For example, denotingN_(PUCCH) ^((1,k)) (where k=0, 1) as a UE-specific starting offset RRCparameter for ePDCCH set k, an n_(offset) value may contain at least oneof N_(PUCCH) ^((1,k=0)) and/or N_(PUCCH) ^((1,k=1)).

The UE specific starting offset values N_(PUCCH) ^((1,k)) may help toefficiently use a given PUCCH resource region by using the RRCparameters in the n_(offset) to offset the PUCCH parameters so thatphysical uplink shared channel (PUSCH) signals may also be transmittedin those PUCCH region depending on eNB scheduling.

In these embodiments, the offset values n_(offset) may be 0, 2,N_(PUCCH) ^((1,k=0)), or N_(PUCCH) ^((1,k=1)). In these embodiments, then_(offset) parameters may therefore be a hybrid version of even numberoffset values and ePDCCH offset values, as described above. Othervariants for n_(offset) may include 0, N, N_(PUCCH) ^((1,k=0))+M₁, orN_(PUCCH) ^((1,k=1))+M₂ where N, M1, and M2 are the integer values. Inthis example, N, M1 and M2 may each be equal to 1 or −1. In someembodiments all three of the variables may be equal to one another, andin other embodiments at least one of the variables may have a value thatis different from the other variables. In other embodiments, N may beequal to 1 or −1, and M1 and/or M2 may be equal to 0. In certainembodiments, N, M1, and M2 may be an even number such as 2, −2, or someother even number to avoid resource collisions by SORTD or FDD channelselection. For example, in these embodiments n_(offset) may be 0, ±2,N_(PUCCH) ^((1,k=0))±2, N_(PUCCH) ^((1,k=1))±2 where “±A” represents +Aor −A.

In a certain embodiments, the offset values n_(offset) for an ePDCCH setk may be 0, 2, N_(PUCCH) ^((1,k=0))−N_(PUCCH) ^((1,k)), or N_(PUCCH)^((1,k=1))−N_(PUCCH) ^((1,k)). In these embodiments, the n_(offset)parameters may therefore effectively change the UE specific startingoffset for an ePDCCH set k into the signaled n_(offset) value, forexample the n_(offset) indicated by ARI as described above. In otherembodiments, other variants for n_(offset) may include 0, N, N_(PUCCH)^((1,k=0))−N_(PUCCH) ^((1,k))+M₁, or N_(PUCCH) ^((1,k=1))−N_(PUCCH)^((1,k))+M₂ where N, M1, and M2 are integer values. In this example, N,M1and M2 may each be equal to 1 or −1. In some embodiments all three ofthe variables may be equal to one another, and in other embodiments atleast one of the variables may have a value that is different from theother variables. In other embodiments, N may be equal to 1 or −1, and M1and/or M2 may be equal to 0. In certain embodiments, N, M1, and M2 maybe an even number such as 2, −2, or some other even number to avoidresource collisions by SORTD or FDD channel selection. For example, inthese embodiments n_(offset) may be 0, ±2, N_(PUCCH)^((1,k=0))−N_(PUCCH) ^((1,k))±2, N_(PUCCH) ^((1,k=1))−N_(PUCCH)^((1,k))±2 where “±A” represents +A or −A. In embodiments where thestarting offset for the second ePDCCH set k=1, N_(PUCCH) ^((1,k=1)), isnot configured, the value of N_(PUCCH) ^((1,k=1)) may be replaced bycell specific starting offset N_(PUCCH) ⁽¹⁾. In these embodiments, thevalues of n_(offset) may then be 0, N, N_(PUCCH) ^((1,k=0))−N_(PUCCH)^((1,k))+M₁, or N_(PUCCH) ⁽¹⁾−N_(PUCCH) ^((1,k))+M₂ where N, M1, and M2are the integer values.

Embodiments of the present disclosure may be implemented into a systemusing any suitable hardware and/or software to configure as desired.FIG. 6 schematically illustrates an example system 600 that may be usedto practice various embodiments described herein. FIG. 6 illustrates,for one embodiment, an example system 600 having one or moreprocessor(s) 605, system control module 610 coupled to at least one ofthe processor(s) 605, system memory 615 coupled to system control module610, non-volatile memory (NVM)/storage 620 coupled to system controlmodule 610, and one or more communications interface(s) 625 coupled tosystem control module 610.

In some embodiments, the system 600 may be capable of functioning as theUE 110 as described herein. In other embodiments, the system 600 may becapable of functioning as the eNB 105 depicted in the embodiment shownin FIG. 1 or any one of the other described embodiments. In someembodiments, the system 600 may include one or more computer-readablemedia (e.g., system memory or NVM/storage 620) having instructions andone or more processors (e.g., processor(s) 605) coupled with the one ormore computer-readable media and configured to execute the instructionsto implement a module to perform actions described herein.

System control module 610 for one embodiment may include any suitableinterface controllers to provide for any suitable interface to at leastone of the processor(s) 605 and/or to any suitable device or componentin communication with system control module 610.

System control module 610 may include memory controller module 630 toprovide an interface to system memory 615. The memory controller module630 may be a hardware module, a software module, and/or a firmwaremodule.

System memory 615 may be used to load and store data and/orinstructions, for example, for system 600. System memory 615 for oneembodiment may include any suitable volatile memory, such as suitableDRAM, for example. In some embodiments, the system memory 615 mayinclude double data rate type four synchronous dynamic random-accessmemory (DDR4 SDRAM).

System control module 610 for one embodiment may include one or moreinput/output (I/O) controller(s) to provide an interface to NVM/storage620 and communications interface(s) 625.

The NVM/storage 620 may be used to store data and/or instructions, forexample. NVM/storage 620 may include any suitable non-volatile memory,such as flash memory, for example, and/or may include any suitablenon-volatile storage device(s), such as one or more hard disk drive(s)(HDD(s)), one or more compact disc (CD) drive(s), and/or one or moredigital versatile disc (DVD) drive(s), for example.

The NVM/storage 620 may include a storage resource physically part of adevice on which the system 600 is installed or it may be accessible by,but not necessarily a part of, the device. For example, the NVM/storage620 may be accessed over a network via the communications interface(s)625.

Communications interface(s) 625 may provide an interface for system 600to communicate over one or more network(s) and/or with any othersuitable device. The system 600 may wirelessly communicate with the oneor more components of the wireless network in accordance with any of oneor more wireless network standards and/or protocols. For example, thecommunications interface(s) 625 may be coupled with the transceivermodule 120 discussed above with respect to FIG. 1.

For one embodiment, at least one of the processor(s) 605 may be packagedtogether with logic for one or more controller(s) of system controlmodule 610, e.g., memory controller module 630. For one embodiment, atleast one of the processor(s) 605 may be packaged together with logicfor one or more controllers of system control module 610 to form aSystem in Package (SiP). For one embodiment, at least one of theprocessor(s) 605 may be integrated on the same die with logic for one ormore controller(s) of system control module 610. For one embodiment, atleast one of the processor(s) 605 may be integrated on the same die withlogic for one or more controller(s) of system control module 610 to forma System on Chip (SoC).

In various embodiments, the system 600 may be, but is not limited to, aserver, a workstation, a desktop computing device, or a mobile computingdevice (e.g., a laptop computing device, a handheld computing device, atablet, a netbook, etc.). In various embodiments, the system 600 mayhave more or less components, and/or different architectures. Forexample, in some embodiments, the system 600 includes one or more of acamera, a keyboard, liquid crystal display (LCD) screen (including touchscreen displays), non-volatile memory port, multiple antennas, graphicschip, application-specific integrated circuit (ASIC), and speakers.

Methods and apparatuses are provided herein for dynamically allocatinguplink control channel resources. In certain embodiments, a UE mayreceive an offset value on an ePDCCH. The UE may further receive one ormore eCCEs of the ePDCCH. Then, the UE may determine allocation of anuplink resource of a PUCCH based at least in part on an index of a firsteCCE of the one or more eCCEs and the offset value. In certainembodiments the offset value may be received in downlink controlinformation transmitted in the ePDCCH, while in other embodiments theoffset value may be based at least in part on an antenna port associatedwith the ePDCCH. In at least one embodiment the antenna port may beallocated to the first eCCE. In some embodiments the allocation of theuplink resource may be based at least in part on a UE specific startingoffset value for a set of the ePDCCH. Additionally the offset value maybe based on the UE specific starting offset value or a cell specificstarting offset value. In some embodiments at least one of the pluralityof offset values may be even or negative, and a scaling factor may beused to multiply the offset value. Additionally, the index of the firsteCCE may be less than an index of other eCCEs of the one or more eCCEs.

Certain embodiments may further include an apparatus with receiving andprocessing circuitry configured to perform functions similar to theembodiments described above. Additionally, the receiving circuitry maybe further configured to obtain one or more CCEs of a PDCCH, and theprocessing circuitry may determine a second allocation of an uplinkresource of the PUCCH based at least in part on an index of a first CCEof the one or more CCEs. In some embodiments the first allocation andthe second allocation may be different from one another.

Other embodiments may include a UE comprising a receiver configured toreceive an offset value and one or more eCCEs of the ePDCCH. The UE mayfurther comprise a processor configured to allocate an uplink resourceof a PUCCH based at least in part on an index of a first eCCE of the oneor more eCCEs and the offset value. The UE may also comprise atransmitter configured to transmit a signal on the physical uplinkcontrol channel using the first uplink resource.

Although certain embodiments have been illustrated and described hereinfor purposes of description, this application is intended to cover anyadaptations or variations of the embodiments discussed herein.Therefore, it is manifestly intended that embodiments described hereinbe limited only by the claims.

Where the disclosure recites “a” or “a first” element or the equivalentthereof, such disclosure includes one or more such elements, neitherrequiring nor excluding two or more such elements. Further, ordinalindicators (e.g., first, second or third) for identified elements areused to distinguish between the elements, and do not indicate or imply arequired or limited number of such elements, nor do they indicate aparticular position or order of such elements unless otherwisespecifically stated.

1. (canceled)
 2. An eNodeB (eNB) comprising: first circuitry to:transmit, on an enhanced physical downlink control channel (ePDCCH), anindication of an offset value selected from a plurality of offset valuescomprising offset values of −2, −1, 0, and 2; and transmit, on theePDCCH, one or more enhanced control channel elements (eCCEs) of theePDCCH; and second circuitry to identify a signal on an uplink resourceof a physical uplink control channel (PUCCH) that is allocated based atleast in part on an index of a first eCCE of the one or more eCCEs andthe selected offset value.
 3. The eNB of claim 2, wherein the firstcircuitry is to transmit the indication of the offset value in downlinkcontrol information transmitted in the ePDCCH.
 4. The eNB of claim 2,wherein the uplink resource is allocated based at least in part on amultiplication of the selected offset value by a scaling factor.
 5. TheeNB of claim 2, wherein the index of the first eCCE is less than anindex of other eCCEs of the one or more eCCEs.
 6. The eNB of claim 2,wherein the uplink resource is allocated based at least in part on astarting offset value for a set of the ePDCCH.
 7. The eNB of claim 6,wherein the starting offset value is a user equipment (UE) specificstarting offset value.
 8. The eNB of claim 7, wherein the selectedoffset value further comprises the UE specific starting offset value ora cell specific starting offset value.
 9. The eNB of claim 2, whereinthe eNB is coupled with an input device.
 10. One or more non-transitorycomputer-readable media comprising instructions to, upon execution ofthe instructions by one or more processors of a user equipment (UE),cause the UE to: monitor an enhanced physical downlink control channel(ePDCCH) for an offset value selected from a set comprising −2, −1, 0,and 2; obtain one or more enhanced control channel elements (eCCEs) ofthe ePDCCH; and determine an allocation of an uplink resource of aphysical uplink control channel (PUCCH) based at least in part on anindex of a first eCCE of the one or more eCCEs and the offset value. 11.The one or more non-transitory computer-readable media of claim 10,wherein the offset value is signaled in downlink control information inthe ePDCCH.
 12. The one or more non-transitory computer-readable mediaof claim 10, wherein the instructions are further to determine the firstallocation based at least in part on a result of the offset valuemultiplied by a scaling factor.
 13. The one or more non-transitorycomputer-readable media of claim 10, wherein the index of the first eCCEis less than an index of other eCCEs of the one or more eCCEs.
 14. Theone or more non-transitory computer-readable media of claim 10, whereinthe instructions are further to determine the first allocation of theuplink resource based at least in part on a starting offset value for aset of the ePDCCH selected from a plurality of sets of the ePDCCH. 15.The one or more non-transitory computer-readable media of claim 14,wherein the starting offset value is a starting offset value specific tothe UE.
 16. The one or more non-transitory computer-readable media ofclaim 15, wherein the offset value is based at least in part on thestarting offset value or a starting offset value specific to a cell. 17.An eNodeB (eNB) comprising: a transmitter to transmit an indication ofan offset value of 2, and one or more enhanced control channel elements(eCCEs) of an enhanced physical downlink control channel (ePDCCH); aprocessor coupled with the receiver, the processor to allocate an uplinkresource of a physical uplink control channel based at least in part onan index of a first eCCE of the one or more eCCEs and the offset value;and a receiver coupled with the transmitter, the receiver to receive asignal on a physical uplink control channel (PUCCH) that uses an uplinkresource that is allocated based at least in part on an index of a firsteCCE of the one or more eCCEs and the offset value.
 18. The eNB of claim17, wherein the transmitter is to transmit the offset value in downlinkcontrol information of the ePDCCH.
 19. The eNB of claim 17, wherein theuplink resource is further based at least in part on the offset value asmultiplied by a scaling factor.
 20. The eNB of claim 17, wherein theindex of the first eCCE is less than an index of other eCCEs of the oneor more eCCEs.
 21. The eNB of claim 17, wherein the uplink resource isallocated based at least in part on a starting offset value for a set ofthe ePDCCH.
 22. The eNB of claim 21, wherein the starting offset valueis specific to a user equipment (UE).
 23. The eNB of claim 22, whereinthe offset value is based at least in part on the starting offset valueor on a starting offset value specific to a cell.
 24. The eNB of claim17, wherein the offset value of 2 is selected from the set consisting of−2, −1, 0, and 2.